-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v2, windows] Handle webview2 process crashes and add DisableWebViewRendererCodeIntegrity flag #2627
Conversation
0ef44af
to
80d64fa
Compare
Deploying with Cloudflare Pages
|
Awesome, thanks for testing 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome job! Thank you 🙏
} | ||
|
||
func (i *ICoreWebView2ProcessFailedEventArgs) GetProcessFailedKind() (COREWEBVIEW2_PROCESS_FAILED_KIND, error) { | ||
kind := COREWEBVIEW2_PROCESS_FAILED_KIND(0xffffffff) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering if this would fail on 32bit (not that we support it! 😅)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just tried it, works fine 😄
Thanks for approving 🙏 |
github.com/wailsapp/wails/v2 v2.5.0 start fail with following errors and blank window on some computer |
There's not really much we can do here against these crashes. The best we can do is to make sure the underlying webview error page is shown, which we tried to achieve with this PR. If that chromium error is not shown this either means the webview is still hidden or the webview itself does not show one. Almost all those crashes are caused by wrongly signed dlls injected into the webview process, which is getting detected and causes the renderer to stop. This is something done in the webview2 by microsoft and ot by Wails. |
I have disabled this feature as prompted, and now it works fine |
I resolved this issue by configuring this environment variable to disable integrity checking. Please note that renderer code integrity checking is a security mechanism that ensures the loaded renderer code has not been tampered with or damaged. Disabling this feature allows bypassing the renderer code integrity check but reduces security. |
Please use the appropriate provided flag for this: wails/v2/pkg/options/windows/windows.go Lines 107 to 115 in c1a0e13
Env variables should not work because we didn't support that for the native webview2loader and this seems to be a bug in the new webview2loader. So this is going to be fixed pretty soon. |
…endererCodeIntegrity flag (#2627) * Add flag to disable webview RendererCodeIntegrity checks * Handle webview2 process crashes
|
This should help for all those issue where no Window comes up: